2024-0630-1120 Questions that bother me along the way - origin time

• type of notes
  #ToBeArchived

Slip-box

To be fleeting notes

Fleeting

To be literature notes (Understanding)

L-Origin

L-My Words

• How to improve as a game designer?

  • Think as an architecture, make features grow
    • Feature design - house
    • System design - city
    • Game design - world
  • Experience design instead of mechanics design
    • Masahiro Sakurai on Creating Games
    • Experience Demo
    • GDC - thatgamecompany
    • EGDS
  • Playtest matters most

• How to implement a feature from A to Z together with ALL job families

  • How the question is raised?
    • Inspired by one page design method, I was trying to use it as the visualization of my design
      • 1 deliver more efficiently
      • 2 easier to read compared with pure text
    • Hard to let everyone aware of current status of the feature
      • Qc weekly smoke test
      • Create weekly review
    • There is not a good way for qc to understand what to test & Duplicate work in both confluence and miro
      • Create flowchart in miro so that everyone is clear about what to expect
    • There is not a good way to let all job families to know the connection between their work and other job families' work
      • Create LoQ-JobFamily table
    • Hard to track production status
      • Link related jiras aside
      • Trying to merge it into miros and create tags to enable auto filter
  • Start from tools
    • Confluence + jira
      • Pros
        • Structured
      • Cons
        • Not good at visualization
        • Hard to make you aware of the connections between your work and other job families' work
        • Hard to track as a whole picture
    • Confluence + jira + miro
      • Miro
        • As the all in one page
      • Confluence
        • As the link storage
      • Jira
        • Task tracking
      • Pros
        • Convenient to check at one places
        • Good visualization
        • Easy to understand the connections between your work and other job families' work
      • Cons (what is missing)
        • Manual maintain for jiras is a pain, if possible, we should try to create auto filter
          • More requirements for PM and QC to use correct tags
  • Understand the core behind the collaboration
    • Responsibility & participation
      • Be responsible
        • Only when you take responsibility for the design, can you inspire others.
      • Everyone owns the design, designer only drives
      • There is no guarantee that your work is what you love, but designers should encourage every job families to use their expertise not only when implementing, but also participating the design to share the ownership together
    • Communication & iteration
      • Design is not fixed, should be iterative based on playtest results

• Main takeaways

  • Keep thinking and learning
    • Expand your thinking to benefit not only yourself but also other job families in the workflow
  • Take chances to ask questions to your lead
    • Which could save a lot of time on some already thought problems
  • Embrace playtest and iterative design
    • Iterative design is not only a method, but also a mindset, means you need to challenge your hypotheses, embrace the failure and keep updating

L-Zotero citation key

To be permanent notes (Complete Ideas)

P-Self Explained Sentences

P-Connection

• relations or differences with other knowledge - 与其他知识的联系或区别
• Parent
  • Caused by::
    -
  • Driven by::
    -
  • Cite from::
    -
• Child
  • Excalidraw::
    -
  • Is source of::
    -
  • Including::
    -
  • Have Example::
    -
  • Contributes to::
    -
• Friend
  • Left
    • Achieved with::
      -
    • Affected by::
      -
    • Supported by::
      -
    • Enhanced by::
      -
    • related::
      -
  • Right
    • against::
      -
    • Opposites::
      -

P-SlipBox

• 将笔记放入对应卡片盒

• 添加双链